@rdiachenko
not adding // violation comments now, i guess will be good to add after the preprocessing recipe is done.
although i am fine if u suggest to add now.

@rdiachenko not adding // violation comments now, i guess will be good to add after the preprocessing recipe is done. although i am fine if u suggest to add now.

Yes, let's do it as a separate step. We need also check related Checkstyle test code to enforce // violation comments, so when there is violation but missed comment, we should fail. In the postprocessing step when we remove // violation it probably makes sense to run Checkstyle again on the output processed file to test Checkstyle doesn't give violations. This way we'll have end-to-end testing